This is a comment left during a code review.
Path: apps/code/src/renderer/features/code-review/utils/resolveDiffSource.test.ts
Line: 1-96

Comment:
**Prefer parameterised tests**

All 8 test cases call the same function with different inputs — this is exactly what `it.each` is for. Per the team's standard, parameterised tests are preferred.

```ts
describe("resolveDiffSource", () => {
  it.each([
    // heuristic (no user choice)
    { configured: null, hasLocalChanges: true,  linkedBranch: "feat/x", aheadOfDefault: 3, expected: "local",  desc: "uncommitted changes → local" },
    { configured: null, hasLocalChanges: false, linkedBranch: "feat/x", aheadOfDefault: 2, expected: "branch", desc: "clean tree with commits ahead → branch" },
    { configured: null, hasLocalChanges: false, linkedBranch: null,     aheadOfDefault: 0, expected: "local",  desc: "no linked branch → local" },
    { configured: null, hasLocalChanges: false, linkedBranch: "feat/x", aheadOfDefault: 0, expected: "local",  desc: "no commits ahead → local" },
    // explicit override
    { configured: "local",  hasLocalChanges: false, linkedBranch: "feat/x", aheadOfDefault: 5, expected: "local",  desc: "explicit local respected even when branch available" },
    { configured: "branch", hasLocalChanges: true,  linkedBranch: "feat/x", aheadOfDefault: 1, expected: "branch", desc: "explicit branch respected when available" },
    { configured: "branch", hasLocalChanges: false, linkedBranch: null,     aheadOfDefault: 0, expected: "local",  desc: "explicit branch falls back to local (no linked branch)" },
    { configured: "branch", hasLocalChanges: false, linkedBranch: "feat/x", aheadOfDefault: 0, expected: "local",  desc: "explicit branch falls back to local (no commits ahead)" },
  ] as const)("$desc", ({ configured, hasLocalChanges, linkedBranch, aheadOfDefault, expected }) => {
    expect(resolveDiffSource({ configured, hasLocalChanges, linkedBranch, aheadOfDefault })).toBe(expected);
  });
});
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: apps/code/src/renderer/features/code-review/components/ReviewPage.tsx
Line: 201-211

Comment:
**Misleading empty state when `repoSlug` is unavailable**

When `repoInfo` is `undefined` (e.g., `useGitQueries` hasn't resolved yet or the remote origin is unset), `repoSlug` is `null` and the query is disabled. `files` stays as `EMPTY_BRANCH_FILES`, so `isLoading` is `false` and `isEmpty` is `true`, causing "No file changes to review" to appear — even though the real issue is that the repo slug couldn't be determined. A user who has commits ahead of default would see this and think the feature is broken.

Consider checking `!repoSlug` explicitly and rendering a distinct message, or keeping `isLoading={isLoading || (!repoSlug && isReviewOpen)}` to show the spinner while metadata is still resolving.

How can I resolve this? If you propose a fix, please make it concise.